Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix up the documentation nav for Spanner. #4054

Merged
merged 2 commits into from
Sep 25, 2017
Merged

Fix up the documentation nav for Spanner. #4054

merged 2 commits into from
Sep 25, 2017

Conversation

lukesneeringer
Copy link
Contributor

Uses #4028 as a base.

This improves the left nav for Spanner and generally makes it make more sense.
Fixes the sixth item on @jonparrott's documentation hotlist.

@lukesneeringer lukesneeringer added the api: spanner Issues related to the Spanner API. label Sep 25, 2017
@lukesneeringer lukesneeringer added this to the Spanner Beta milestone Sep 25, 2017
@lukesneeringer lukesneeringer self-assigned this Sep 25, 2017
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Sep 25, 2017
@theacodes theacodes mentioned this pull request Sep 25, 2017
Merged
7 tasks
@lukesneeringer lukesneeringer merged commit 2459682 into googleapis:spanner-beta Sep 25, 2017
@lukesneeringer lukesneeringer deleted the docs-toctree branch September 25, 2017 20:24
lukesneeringer added a commit that referenced this pull request Sep 26, 2017
@lukesneeringer
Fix up the documentation nav for Spanner. (#4054)
a35d84a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@theacodes theacodes theacodes approved these changes

@tseaver tseaver tseaver approved these changes

Assignees

@lukesneeringer lukesneeringer

Labels
api: spanner Issues related to the Spanner API. cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@lukesneeringer @tseaver @theacodes @googlebot